Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7d67fd8cd034e631da9aaa39dd1f2f212c351058a4345c1469d6ddb0fa1e347

Tx prefix hash: 49e9b93cb3f315eb94a56582987275005c9d4566ad5ea33666cbc0ca5f3d72d2
Tx public key: 0d6cac56d589c0950f60234aa570258606d0e860887229edd13999d2fbf87510
Timestamp: 1699199016 Timestamp [UCT]: 2023-11-05 15:43:36 Age [y:d:h:m:s]: 01:184:12:09:35
Block: 885107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393075 RingCT/type: yes/0
Extra: 010d6cac56d589c0950f60234aa570258606d0e860887229edd13999d2fbf875100211000000014b8f5122000000000000000000

1 output(s) for total of 0.716593870000 dcy

stealth address amount amount idx
00: 5848717e28d72cd72842f221a20dc379f01ca0eb07ea8c574482dc39b2d32b59 0.716593870000 1340860 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": 885117, "vin": [ { "gen": { "height": 885107 } } ], "vout": [ { "amount": 716593870, "target": { "key": "5848717e28d72cd72842f221a20dc379f01ca0eb07ea8c574482dc39b2d32b59" } } ], "extra": [ 1, 13, 108, 172, 86, 213, 137, 192, 149, 15, 96, 35, 74, 165, 112, 37, 134, 6, 208, 232, 96, 136, 114, 41, 237, 209, 57, 153, 210, 251, 248, 117, 16, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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