Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d815f89f727898cc41e1190e80a0973588fadebee53bfb85f66a8494257c948c

Tx prefix hash: 25ddd23b1a43c91377c206fed61c9b70a866cf8fcb3daaf50fd89f3bf67ec643
Tx public key: 2a05354ad1ce844189e962eab39c8b9d4a5c033d2c505b6e9376911524b21530
Timestamp: 1705281808 Timestamp [UCT]: 2024-01-15 01:23:28 Age [y:d:h:m:s]: 01:310:20:36:49
Block: 935500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481018 RingCT/type: yes/0
Extra: 012a05354ad1ce844189e962eab39c8b9d4a5c033d2c505b6e9376911524b2153002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01a1b8dcd7dc8d02e8e603924884807504f5ee433c4dbdfd433a5c7899e11189 0.600000000000 1393516 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": 935510, "vin": [ { "gen": { "height": 935500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01a1b8dcd7dc8d02e8e603924884807504f5ee433c4dbdfd433a5c7899e11189" } } ], "extra": [ 1, 42, 5, 53, 74, 209, 206, 132, 65, 137, 233, 98, 234, 179, 156, 139, 157, 74, 92, 3, 61, 44, 80, 91, 110, 147, 118, 145, 21, 36, 178, 21, 48, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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