Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93fa7b164c7f05b324cc20bf168d8073e05f6653048a7f4c7407dbc4ee60f844

Tx prefix hash: 521200abcab06efa0de0610280871d3ce1f9f1010c51c0591457d64947ab1de3
Tx public key: 488c1851278c1944bbb86084a9526f4b7cd74796aef83a4c5aeb3d5a4e7da0e2
Timestamp: 1712256084 Timestamp [UCT]: 2024-04-04 18:41:24 Age [y:d:h:m:s]: 01:228:00:19:22
Block: 993337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421666 RingCT/type: yes/0
Extra: 01488c1851278c1944bbb86084a9526f4b7cd74796aef83a4c5aeb3d5a4e7da0e20211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b94a5a5411451a6001a39abb34c15c7e643688b6a3961cc5464f3f6678d2f9d9 0.600000000000 1453723 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": 993347, "vin": [ { "gen": { "height": 993337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b94a5a5411451a6001a39abb34c15c7e643688b6a3961cc5464f3f6678d2f9d9" } } ], "extra": [ 1, 72, 140, 24, 81, 39, 140, 25, 68, 187, 184, 96, 132, 169, 82, 111, 75, 124, 215, 71, 150, 174, 248, 58, 76, 90, 235, 61, 90, 78, 125, 160, 226, 2, 17, 0, 0, 0, 6, 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