Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d3d1adc0777501aa96e0b2a8b729aee23872a6885e28b9590e9b3afad5b3fcd

Tx prefix hash: 63cbeccdd5defc4a2b07a7a80d6fafd635ce0f8e9ae3bb8eee0b43c3f02616d6
Tx public key: 767bbb408bb596e5d7a02b6ac9858f71a1d93c553bcaee52f2302c6cb1d2df68
Timestamp: 1745782044 Timestamp [UCT]: 2025-04-27 19:27:24 Age [y:d:h:m:s]: 00:208:03:53:54
Block: 1270789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146484 RingCT/type: yes/0
Extra: 01767bbb408bb596e5d7a02b6ac9858f71a1d93c553bcaee52f2302c6cb1d2df6802110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bfe045078d4ddd967f6e4660fdef23577869a02ab9291fad789a7e2599f771b 0.600000000000 1758034 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": 1270799, "vin": [ { "gen": { "height": 1270789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bfe045078d4ddd967f6e4660fdef23577869a02ab9291fad789a7e2599f771b" } } ], "extra": [ 1, 118, 123, 187, 64, 139, 181, 150, 229, 215, 160, 43, 106, 201, 133, 143, 113, 161, 217, 60, 85, 59, 202, 238, 82, 242, 48, 44, 108, 177, 210, 223, 104, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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