Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ad7a21fb3694b25dca2eedd60483ba5efaf9ab3c3e6d1031ab84ede1a048cb7

Tx prefix hash: 08c65b86544100fe18c3c8edddbf029e6a07f8641114c7cbf2b3a9d72d722833
Tx public key: 4e23d5273a7977884a29dc1f4e69597140f8c6f62314c4c3675c7c6a6bdd9621
Timestamp: 1699885983 Timestamp [UCT]: 2023-11-13 14:33:03 Age [y:d:h:m:s]: 01:146:06:55:34
Block: 890805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365718 RingCT/type: yes/0
Extra: 014e23d5273a7977884a29dc1f4e69597140f8c6f62314c4c3675c7c6a6bdd9621021100000003faf35c9c000000000000000000

1 output(s) for total of 0.686109197000 dcy

stealth address amount amount idx
00: dc8974c1f36649b3d6b61a7961acfa79aad3dbdf8a292c97da07eccf39535379 0.686109197000 1346836 of 0

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": 890815, "vin": [ { "gen": { "height": 890805 } } ], "vout": [ { "amount": 686109197, "target": { "key": "dc8974c1f36649b3d6b61a7961acfa79aad3dbdf8a292c97da07eccf39535379" } } ], "extra": [ 1, 78, 35, 213, 39, 58, 121, 119, 136, 74, 41, 220, 31, 78, 105, 89, 113, 64, 248, 198, 246, 35, 20, 196, 195, 103, 92, 124, 106, 107, 221, 150, 33, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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