Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f482245a4633ffcdc142755e05200bccc4dd97fcf485325135e2ef7bfa703a5

Tx prefix hash: ab60a5c925f63698c39b8704fd80d59dccd22ebef4c6a4d2c2c4dd8bab05eeb2
Tx public key: 77654c0dd69424d41a336633c8c9b71b9601ed1f402dc7004a1304674636f924
Timestamp: 1761242747 Timestamp [UCT]: 2025-10-23 18:05:47 Age [y:d:h:m:s]: 00:096:18:18:24
Block: 1396373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69091 RingCT/type: yes/0
Extra: 0177654c0dd69424d41a336633c8c9b71b9601ed1f402dc7004a1304674636f924021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21a65f4d4d10ad996c8099a74ece87c49181af0b6891e80a629c504f88215f7e 0.600000000000 1884658 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": 1396383, "vin": [ { "gen": { "height": 1396373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21a65f4d4d10ad996c8099a74ece87c49181af0b6891e80a629c504f88215f7e" } } ], "extra": [ 1, 119, 101, 76, 13, 214, 148, 36, 212, 26, 51, 102, 51, 200, 201, 183, 27, 150, 1, 237, 31, 64, 45, 199, 0, 74, 19, 4, 103, 70, 54, 249, 36, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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