Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eae2a103236884b317adef1239083357c8f13db4f0d1a808db4a137ce720a3ce

Tx prefix hash: 47c7e68043d9f4a3b269ed800447a91fd77b4d1b8ec04c509fa7f5fd9e807d8c
Tx public key: e6e203d82a8fc47bb0d0173031d1d2680ecfac19528c853a8c994a1dff8a5388
Timestamp: 1712844491 Timestamp [UCT]: 2024-04-11 14:08:11 Age [y:d:h:m:s]: 01:036:22:21:40
Block: 998204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287391 RingCT/type: yes/0
Extra: 01e6e203d82a8fc47bb0d0173031d1d2680ecfac19528c853a8c994a1dff8a53880211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53cdd4c6f28daaa9a987e22b26e0e7880fc60bc32c789d64a4a510451baf934e 0.600000000000 1458650 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": 998214, "vin": [ { "gen": { "height": 998204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53cdd4c6f28daaa9a987e22b26e0e7880fc60bc32c789d64a4a510451baf934e" } } ], "extra": [ 1, 230, 226, 3, 216, 42, 143, 196, 123, 176, 208, 23, 48, 49, 209, 210, 104, 14, 207, 172, 25, 82, 140, 133, 58, 140, 153, 74, 29, 255, 138, 83, 136, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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