Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 888f5df5d4bed4be87a4bf01a4babcb003b69b695fb95e2612bf943abde3691f

Tx prefix hash: 30ba89f5db8da89647af617a9c4bdf9be0f2970893694a2caa08d16b05127b0c
Tx public key: a576a932d80bad01acb589d2936ecd29acf0ed17ea9b7ef6e279fa3d44a7a04b
Timestamp: 1750000684 Timestamp [UCT]: 2025-06-15 15:18:04 Age [y:d:h:m:s]: 00:151:19:28:18
Block: 1305609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106284 RingCT/type: yes/0
Extra: 01a576a932d80bad01acb589d2936ecd29acf0ed17ea9b7ef6e279fa3d44a7a04b0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68c5563396a691afbe591244c10fc8274dd32e816b6ca4a8a2ef867887e1a2b8 0.600000000000 1793210 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 dinasty-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": 1305619, "vin": [ { "gen": { "height": 1305609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68c5563396a691afbe591244c10fc8274dd32e816b6ca4a8a2ef867887e1a2b8" } } ], "extra": [ 1, 165, 118, 169, 50, 216, 11, 173, 1, 172, 181, 137, 210, 147, 110, 205, 41, 172, 240, 237, 23, 234, 155, 126, 246, 226, 121, 250, 61, 68, 167, 160, 75, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8