Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00da6688c7a01b5a2ce58494f512c4852d243629fa81495d11d804f91189e681

Tx prefix hash: cb1caed0672163911bc072f7b7e95a2a344d89a444525176130c99ce386f2589
Tx public key: 32e5bf1406a8ddd94657840a58c9ed439a0bb145c88f1f21be5b7d3a759c0c8c
Timestamp: 1727986577 Timestamp [UCT]: 2024-10-03 20:16:17 Age [y:d:h:m:s]: 00:110:16:46:15
Block: 1123776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79095 RingCT/type: yes/0
Extra: 0132e5bf1406a8ddd94657840a58c9ed439a0bb145c88f1f21be5b7d3a759c0c8c02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 336b4077c09fd12571fe9051f9a51e2991cd8e83fedc2c0017659697239a5fd7 0.600000000000 1606311 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": 1123786, "vin": [ { "gen": { "height": 1123776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "336b4077c09fd12571fe9051f9a51e2991cd8e83fedc2c0017659697239a5fd7" } } ], "extra": [ 1, 50, 229, 191, 20, 6, 168, 221, 217, 70, 87, 132, 10, 88, 201, 237, 67, 154, 11, 177, 69, 200, 143, 31, 33, 190, 91, 125, 58, 117, 156, 12, 140, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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