Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 540e94eaccf07731c5e9cab0447a493b598aa57fde8b1b4e44bf989aed2bd1de

Tx prefix hash: 490a79f0516848d635650a3481c977f355b7f5a28f6d69a729bd81ec372064ac
Tx public key: 6fa2274f2de422a2ec1aa26ca0cfe235cad6ca7bbdf21bbd08f2111a2c43685e
Timestamp: 1725574145 Timestamp [UCT]: 2024-09-05 22:09:05 Age [y:d:h:m:s]: 00:212:14:13:25
Block: 1103774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151769 RingCT/type: yes/0
Extra: 016fa2274f2de422a2ec1aa26ca0cfe235cad6ca7bbdf21bbd08f2111a2c43685e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5faf001df6fcac0b02f3420fc45ac5f3f67aa287b6b856625631025f316d9c86 0.600000000000 1580731 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": 1103784, "vin": [ { "gen": { "height": 1103774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5faf001df6fcac0b02f3420fc45ac5f3f67aa287b6b856625631025f316d9c86" } } ], "extra": [ 1, 111, 162, 39, 79, 45, 228, 34, 162, 236, 26, 162, 108, 160, 207, 226, 53, 202, 214, 202, 123, 189, 242, 27, 189, 8, 242, 17, 26, 44, 67, 104, 94, 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