Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12bc5544535b45e3bc07f77ec337a1a90e11985ad5e446534aa91566024adc39

Tx prefix hash: e4b0916d2eadb4c5b9b9119fbd01550fb150e9628c9cd003ced63ceb0eacc82c
Tx public key: 1948a231c3f906e220d3fb67ab82b5fa1b0df8daec725bc878f796183faf4235
Timestamp: 1730529257 Timestamp [UCT]: 2024-11-02 06:34:17 Age [y:d:h:m:s]: 00:152:19:08:42
Block: 1144759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109035 RingCT/type: yes/0
Extra: 011948a231c3f906e220d3fb67ab82b5fa1b0df8daec725bc878f796183faf42350211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52f773046f1f84fedf567d0bdc5656c7afcf3c6b99a6b21e038d2be3164a4b77 0.600000000000 1629058 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": 1144769, "vin": [ { "gen": { "height": 1144759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52f773046f1f84fedf567d0bdc5656c7afcf3c6b99a6b21e038d2be3164a4b77" } } ], "extra": [ 1, 25, 72, 162, 49, 195, 249, 6, 226, 32, 211, 251, 103, 171, 130, 181, 250, 27, 13, 248, 218, 236, 114, 91, 200, 120, 247, 150, 24, 63, 175, 66, 53, 2, 17, 0, 0, 0, 1, 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