Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7022958dc4e8b2f202b9e5d599703b3ff4ba213d0d6cd1efbf1f29fd484fbc8

Tx prefix hash: 1be5051dc186cdf865ff19540d874e4dbc00dcebdf398c9279d61ec6802682e7
Tx public key: 7e9b1c7148ffa51951bb35954614e9c1c46921d55e013b4181309e6d6b485c03
Timestamp: 1765262348 Timestamp [UCT]: 2025-12-09 06:39:08 Age [y:d:h:m:s]: 00:042:21:52:10
Block: 1429663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30587 RingCT/type: yes/0
Extra: 017e9b1c7148ffa51951bb35954614e9c1c46921d55e013b4181309e6d6b485c0302110000000b70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63b740164aa75ecfad2e20aaefb254e411f4c0fa59503e8af94b56179cc142f5 0.600000000000 1918394 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": 1429673, "vin": [ { "gen": { "height": 1429663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63b740164aa75ecfad2e20aaefb254e411f4c0fa59503e8af94b56179cc142f5" } } ], "extra": [ 1, 126, 155, 28, 113, 72, 255, 165, 25, 81, 187, 53, 149, 70, 20, 233, 193, 196, 105, 33, 213, 94, 1, 59, 65, 129, 48, 158, 109, 107, 72, 92, 3, 2, 17, 0, 0, 0, 11, 112, 96, 157, 3, 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