Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8f30c637f116f613cc894eb47d4c2d7e6b46f54e29a50e1e3bc316f423e78ce

Tx prefix hash: 2600edfe13bc742a2276a01be03ab50431398014f0424ae61d66d7a4d070baf9
Tx public key: ca38ad5f4b5636b4b57d1bfb6b07e8397db50b0c41558450e16aecacbcb35d59
Timestamp: 1729326940 Timestamp [UCT]: 2024-10-19 08:35:40 Age [y:d:h:m:s]: 00:154:08:47:33
Block: 1134877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110102 RingCT/type: yes/0
Extra: 01ca38ad5f4b5636b4b57d1bfb6b07e8397db50b0c41558450e16aecacbcb35d590211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7701e7272055fb04f67d7ecdc2987a3715649e7201b24ade74e0cd7bad9b76d2 0.600000000000 1618204 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": 1134887, "vin": [ { "gen": { "height": 1134877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7701e7272055fb04f67d7ecdc2987a3715649e7201b24ade74e0cd7bad9b76d2" } } ], "extra": [ 1, 202, 56, 173, 95, 75, 86, 54, 180, 181, 125, 27, 251, 107, 7, 232, 57, 125, 181, 11, 12, 65, 85, 132, 80, 225, 106, 236, 172, 188, 179, 93, 89, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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