Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 467b88e80bd8bdf264cfc7cbd45042a9eca9b08deec9728db19e8b6387736480

Tx prefix hash: d76b9d9554f82534f0add6722f092481f6cae0faf0c3bec26dd3c11a2e1089d0
Tx public key: 6a3428a2bc0c1042d4ef538bb047b53b599e2693530d5eee3ead71a561daabcf
Timestamp: 1704918660 Timestamp [UTC]: 2024-01-10 20:31:00 Age [y:d:h:m:s]: 02:127:02:05:59
Block: 932509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 602908 RingCT/type: yes/0
Extra: 016a3428a2bc0c1042d4ef538bb047b53b599e2693530d5eee3ead71a561daabcf02110000000852d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fa822ca3f6ec9795486e1509fe84eb539337ffe095ef879896131bf0c97d5411 0.000600000000 1390445 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 932519, "vin": [ { "gen": { "height": 932509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa822ca3f6ec9795486e1509fe84eb539337ffe095ef879896131bf0c97d5411" } } ], "extra": [ 1, 106, 52, 40, 162, 188, 12, 16, 66, 212, 239, 83, 139, 176, 71, 181, 59, 89, 158, 38, 147, 83, 13, 94, 238, 62, 173, 113, 165, 97, 218, 171, 207, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: