Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d07256d762183e1d451494fd9b51d03fad3295f0a1ebfb3329c4c749bd376221

Tx prefix hash: df54be1f54679a94a8e3fa4e8dceaa73922e762732571808f392acf2f118d150
Tx public key: 4e48b81dfa46a950b7dc4628499b31a66e0286b8902be71bb28fd5f3a301dfad
Timestamp: 1750915562 Timestamp [UCT]: 2025-06-26 05:26:02 Age [y:d:h:m:s]: 00:147:20:06:20
Block: 1312977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103639 RingCT/type: yes/0
Extra: 014e48b81dfa46a950b7dc4628499b31a66e0286b8902be71bb28fd5f3a301dfad0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd6664ead1f9b17e6e83b69a9c919cf2ee733c00c9e9e99d240fbebfb07ece11 0.600000000000 1800614 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": 1312987, "vin": [ { "gen": { "height": 1312977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd6664ead1f9b17e6e83b69a9c919cf2ee733c00c9e9e99d240fbebfb07ece11" } } ], "extra": [ 1, 78, 72, 184, 29, 250, 70, 169, 80, 183, 220, 70, 40, 73, 155, 49, 166, 110, 2, 134, 184, 144, 43, 231, 27, 178, 143, 213, 243, 163, 1, 223, 173, 2, 17, 0, 0, 0, 1, 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