Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2ed150881dc2355c893d3d8d4b6c59915c54ee889aad0812988fe9cda9cf8f0

Tx prefix hash: 12881f21e1a1d367fd276ae0f6548d1dad0e1ead57b7e955713469b8e985089a
Tx public key: 43abf846196322b8bc9a340d0164680244e42923c64df114fd1dfa257ae5420f
Timestamp: 1754910467 Timestamp [UCT]: 2025-08-11 11:07:47 Age [y:d:h:m:s]: 00:108:19:19:06
Block: 1344766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77021 RingCT/type: yes/0
Extra: 0143abf846196322b8bc9a340d0164680244e42923c64df114fd1dfa257ae5420f02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af619fb2e3f3aff195e0dccac46c038cccd0ecac0a5e1fa15b38c8c0090ec3c5 0.600000000000 1832651 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": 1344776, "vin": [ { "gen": { "height": 1344766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af619fb2e3f3aff195e0dccac46c038cccd0ecac0a5e1fa15b38c8c0090ec3c5" } } ], "extra": [ 1, 67, 171, 248, 70, 25, 99, 34, 184, 188, 154, 52, 13, 1, 100, 104, 2, 68, 228, 41, 35, 198, 77, 241, 20, 253, 29, 250, 37, 122, 229, 66, 15, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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