Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57482f3becd38a4092dc7823c981011e9e3f3a1890860a304f1eb0f93308e594

Tx prefix hash: a3e162f320b74c02fffb69c25920523f7d2747b6600bb530765460c22ab88416
Tx public key: 7e4dea807fb3296cce086f8fbbcbc68e5e1e2d0234e267b45a9b7d7c3dc9e70e
Timestamp: 1712861434 Timestamp [UCT]: 2024-04-11 18:50:34 Age [y:d:h:m:s]: 00:339:08:05:28
Block: 998350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242624 RingCT/type: yes/0
Extra: 017e4dea807fb3296cce086f8fbbcbc68e5e1e2d0234e267b45a9b7d7c3dc9e70e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efac11c6938d2f5e0c3e18bf8c171021b109cb0e00a2ff339a75eec45b227719 0.600000000000 1458796 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": 998360, "vin": [ { "gen": { "height": 998350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efac11c6938d2f5e0c3e18bf8c171021b109cb0e00a2ff339a75eec45b227719" } } ], "extra": [ 1, 126, 77, 234, 128, 127, 179, 41, 108, 206, 8, 111, 143, 187, 203, 198, 142, 94, 30, 45, 2, 52, 226, 103, 180, 90, 155, 125, 124, 61, 201, 231, 14, 2, 17, 0, 0, 0, 3, 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