Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46d18f32681f6abcc75e2741dce54a462d783f41926386598d9c328cd7580595

Tx prefix hash: fe71dc303200007e7716afe7c8ed3d00554b36c7b1322fa2020a03763919e992
Tx public key: 7eacfd3b8c20b8b2ab509b39d56d126da9c68ccc7800f75a739b58527d0f3a64
Timestamp: 1706246938 Timestamp [UCT]: 2024-01-26 05:28:58 Age [y:d:h:m:s]: 01:287:21:31:14
Block: 943503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464574 RingCT/type: yes/0
Extra: 017eacfd3b8c20b8b2ab509b39d56d126da9c68ccc7800f75a739b58527d0f3a6402110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6a1e093dab04ec603ca800f7b37606945936abde7400e50e02bf9f4eb709ddc 0.600000000000 1401711 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": 943513, "vin": [ { "gen": { "height": 943503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6a1e093dab04ec603ca800f7b37606945936abde7400e50e02bf9f4eb709ddc" } } ], "extra": [ 1, 126, 172, 253, 59, 140, 32, 184, 178, 171, 80, 155, 57, 213, 109, 18, 109, 169, 198, 140, 204, 120, 0, 247, 90, 115, 155, 88, 82, 125, 15, 58, 100, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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