Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee5a4b1614dbd65391c68dac36ff971bf5618a48f5903008720eec797d5b6bc2

Tx prefix hash: 23bfcd7dfd86146a9ad183506ff106c4b29d92a5d569d859f8edf14a1bc0d5bb
Tx public key: 99661e3a6a42148c8fdbf7a4de7023bbae4f049f7e6c723cf454c1fbaf8c5190
Timestamp: 1752888722 Timestamp [UCT]: 2025-07-19 01:32:02 Age [y:d:h:m:s]: 00:082:03:18:24
Block: 1328500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57447 RingCT/type: yes/0
Extra: 0199661e3a6a42148c8fdbf7a4de7023bbae4f049f7e6c723cf454c1fbaf8c5190021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f87d246480d903b7491adc6d3a53e69505765f37956109af99e11279299d65bf 0.600000000000 1816263 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": 1328510, "vin": [ { "gen": { "height": 1328500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f87d246480d903b7491adc6d3a53e69505765f37956109af99e11279299d65bf" } } ], "extra": [ 1, 153, 102, 30, 58, 106, 66, 20, 140, 143, 219, 247, 164, 222, 112, 35, 187, 174, 79, 4, 159, 126, 108, 114, 60, 244, 84, 193, 251, 175, 140, 81, 144, 2, 17, 0, 0, 0, 2, 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