Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7c4ac459c02453317f2e94a596b5d68606928b2a8cb603af56a00cd8a389776

Tx prefix hash: 793d330ced1fffee243725e06f2e5b99079c42da0ba0f7cea629a6253a5f1729
Tx public key: dd0a7b73c92fd2e3cecc50c3f4358e3d682d522ef387edd1c8665e81f1851d60
Timestamp: 1731664265 Timestamp [UCT]: 2024-11-15 09:51:05 Age [y:d:h:m:s]: 00:160:01:51:55
Block: 1154167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114245 RingCT/type: yes/0
Extra: 01dd0a7b73c92fd2e3cecc50c3f4358e3d682d522ef387edd1c8665e81f1851d60021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e37d86fc874a398ced895ec019596d0abb83f4aa9587616d78bd0f60b22887f2 0.600000000000 1639778 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": 1154177, "vin": [ { "gen": { "height": 1154167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e37d86fc874a398ced895ec019596d0abb83f4aa9587616d78bd0f60b22887f2" } } ], "extra": [ 1, 221, 10, 123, 115, 201, 47, 210, 227, 206, 204, 80, 195, 244, 53, 142, 61, 104, 45, 82, 46, 243, 135, 237, 209, 200, 102, 94, 129, 241, 133, 29, 96, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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