Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 987d1892231e1216faf68828ab40461d6f974f5d3e185016be5638dbc7426d08

Tx prefix hash: 453da2337e82ea71ba8179689767468500fed9a9ab4df262b795351c1a4f9ec0
Tx public key: d5c478669e0eeb770d96d713d6406d3dc645926e191c5449d16f58f8c4cbe530
Timestamp: 1709321726 Timestamp [UCT]: 2024-03-01 19:35:26 Age [y:d:h:m:s]: 01:046:19:15:55
Block: 969037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294446 RingCT/type: yes/0
Extra: 01d5c478669e0eeb770d96d713d6406d3dc645926e191c5449d16f58f8c4cbe5300211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea8dacdea0845461d724606b964104c3fedf43289ba38208234d7ae5fbdae7f3 0.600000000000 1428864 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": 969047, "vin": [ { "gen": { "height": 969037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea8dacdea0845461d724606b964104c3fedf43289ba38208234d7ae5fbdae7f3" } } ], "extra": [ 1, 213, 196, 120, 102, 158, 14, 235, 119, 13, 150, 215, 19, 214, 64, 109, 61, 198, 69, 146, 110, 25, 28, 84, 73, 209, 111, 88, 248, 196, 203, 229, 48, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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