Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a2e2331d9e3df76906d502cdeb68ad1be1483d9d070bebf2ecb1475f72cb132

Tx prefix hash: 762dd63f6c2a1f763b354c4f2df00d1ce4aa38a1b18bcbf4d7733ec048b20eb8
Tx public key: f9dbcea100b088d811fefce014fc1baf427b7c4e65f3dfbe0afccf914441ffaf
Timestamp: 1697021907 Timestamp [UCT]: 2023-10-11 10:58:27 Age [y:d:h:m:s]: 01:245:03:00:06
Block: 867260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436230 RingCT/type: yes/0
Extra: 01f9dbcea100b088d811fefce014fc1baf427b7c4e65f3dfbe0afccf914441ffaf02110000000f4b8f5122000000000000000000

1 output(s) for total of 0.821121899000 dcy

stealth address amount amount idx
00: c471c238d4705a036d456a0631f213cbf0f4af776b96dfc9e72e0e94b02cfd81 0.821121899000 1321934 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": 867270, "vin": [ { "gen": { "height": 867260 } } ], "vout": [ { "amount": 821121899, "target": { "key": "c471c238d4705a036d456a0631f213cbf0f4af776b96dfc9e72e0e94b02cfd81" } } ], "extra": [ 1, 249, 219, 206, 161, 0, 176, 136, 216, 17, 254, 252, 224, 20, 252, 27, 175, 66, 123, 124, 78, 101, 243, 223, 190, 10, 252, 207, 145, 68, 65, 255, 175, 2, 17, 0, 0, 0, 15, 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