Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9e02cb19ebf1d14f24e7d9a30245eae90994b8cf3b0845531a3055d50927515

Tx prefix hash: 0fc37db8531e5fa93e01dc696d04aa87ec71af1d2cafba5f36622bac58a3728d
Tx public key: 98a49901e2ed9f3f3754f69354237149f2db010d640a00bd510de5457573a0b9
Timestamp: 1754021308 Timestamp [UCT]: 2025-08-01 04:08:28 Age [y:d:h:m:s]: 00:065:19:00:42
Block: 1337790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45818 RingCT/type: yes/0
Extra: 0198a49901e2ed9f3f3754f69354237149f2db010d640a00bd510de5457573a0b9021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f628e0404a74545a7da3f3acec63ab0de192649cafddfd5e979ac1d0e622d5ea 0.600000000000 1825595 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": 1337800, "vin": [ { "gen": { "height": 1337790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f628e0404a74545a7da3f3acec63ab0de192649cafddfd5e979ac1d0e622d5ea" } } ], "extra": [ 1, 152, 164, 153, 1, 226, 237, 159, 63, 55, 84, 246, 147, 84, 35, 113, 73, 242, 219, 1, 13, 100, 10, 0, 189, 81, 13, 229, 69, 117, 115, 160, 185, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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