Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 243eb1f09588d5caaf32d5fd0afafa8036dcbad057c8ae56c80a114fb383d369

Tx prefix hash: 8ca24b4d1bdc9d0884d2cf4ca37c259d9979b74699e79d30011122d0b5e12b99
Tx public key: e5c3f442c2f0e4ea9930b7b71ad0bf922d2b9e818cb9c6b74934dbeadc49ec36
Timestamp: 1707411547 Timestamp [UCT]: 2024-02-08 16:59:07 Age [y:d:h:m:s]: 01:054:16:01:44
Block: 953181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300116 RingCT/type: yes/0
Extra: 01e5c3f442c2f0e4ea9930b7b71ad0bf922d2b9e818cb9c6b74934dbeadc49ec3602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 589ce62471d63f9c92eef07f48d2f271aac242c296728fc605b2bc2453ccfc7c 0.600000000000 1412357 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": 953191, "vin": [ { "gen": { "height": 953181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "589ce62471d63f9c92eef07f48d2f271aac242c296728fc605b2bc2453ccfc7c" } } ], "extra": [ 1, 229, 195, 244, 66, 194, 240, 228, 234, 153, 48, 183, 183, 26, 208, 191, 146, 45, 43, 158, 129, 140, 185, 198, 183, 73, 52, 219, 234, 220, 73, 236, 54, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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