Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2fc28328fce02f529da8feada9b0f17aca0d497b5fb0615a131c00cd476d040

Tx prefix hash: 903d16d9bbcb3adbd924bf69cc013f6bc003865705a6eeb7feb74b168a6aa7ec
Tx public key: 0464b02531b2e7e24296335edcdaeecd121f48d2b5e80defc487719c106d0d9c
Timestamp: 1700487452 Timestamp [UCT]: 2023-11-20 13:37:32 Age [y:d:h:m:s]: 01:181:23:55:15
Block: 895779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391291 RingCT/type: yes/0
Extra: 010464b02531b2e7e24296335edcdaeecd121f48d2b5e80defc487719c106d0d9c0211000000034b8f5122000000000000000000

1 output(s) for total of 0.660560054000 dcy

stealth address amount amount idx
00: 198e0bf71ad6ce93052566d51023980dfb09d5cc609bbd108beb570480545ecb 0.660560054000 1352026 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": 895789, "vin": [ { "gen": { "height": 895779 } } ], "vout": [ { "amount": 660560054, "target": { "key": "198e0bf71ad6ce93052566d51023980dfb09d5cc609bbd108beb570480545ecb" } } ], "extra": [ 1, 4, 100, 176, 37, 49, 178, 231, 226, 66, 150, 51, 94, 220, 218, 238, 205, 18, 31, 72, 210, 181, 232, 13, 239, 196, 135, 113, 156, 16, 109, 13, 156, 2, 17, 0, 0, 0, 3, 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