Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56a8c933f71d2428d851ad989c90ec716c6debcf8b2222a2fddbdd09b3604dd3

Tx prefix hash: fc7484a8cfc389c33d6665c76a8a6f542d9228524af8c55ed1a87f4dd31174dc
Tx public key: cda2afae8a2b23ab6f82c667eba67cc5a890ef15f02d2d5800630b4279d1c6af
Timestamp: 1721968509 Timestamp [UCT]: 2024-07-26 04:35:09 Age [y:d:h:m:s]: 00:255:22:20:47
Block: 1073871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182815 RingCT/type: yes/0
Extra: 01cda2afae8a2b23ab6f82c667eba67cc5a890ef15f02d2d5800630b4279d1c6af021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70be5f5bc7ed6f6cfd9ef028827b545e8936fa63dec3f826a464c126c83cdd68 0.600000000000 1546378 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": 1073881, "vin": [ { "gen": { "height": 1073871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70be5f5bc7ed6f6cfd9ef028827b545e8936fa63dec3f826a464c126c83cdd68" } } ], "extra": [ 1, 205, 162, 175, 174, 138, 43, 35, 171, 111, 130, 198, 103, 235, 166, 124, 197, 168, 144, 239, 21, 240, 45, 45, 88, 0, 99, 11, 66, 121, 209, 198, 175, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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