Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 387a763014bb269fc00cf3edbdeeb631abd9031da62945ddcabeade455c02a98

Tx prefix hash: 984da8e2f6a5ab8ff797a5c5b980fa1c3cbddda9d10a7312827d745ffd911de0
Tx public key: a0178d46742effb4ecf01461c323c899f70bd56ca25c0539cc0fb5a5e4b730f6
Timestamp: 1710841200 Timestamp [UCT]: 2024-03-19 09:40:00 Age [y:d:h:m:s]: 01:230:12:46:18
Block: 981643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423433 RingCT/type: yes/0
Extra: 01a0178d46742effb4ecf01461c323c899f70bd56ca25c0539cc0fb5a5e4b730f602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45272d693a090479109d670d0bc225f03de8cbd9ee3e28901ad3b94eaa424e3e 0.600000000000 1441740 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": 981653, "vin": [ { "gen": { "height": 981643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45272d693a090479109d670d0bc225f03de8cbd9ee3e28901ad3b94eaa424e3e" } } ], "extra": [ 1, 160, 23, 141, 70, 116, 46, 255, 180, 236, 240, 20, 97, 195, 35, 200, 153, 247, 11, 213, 108, 162, 92, 5, 57, 204, 15, 181, 165, 228, 183, 48, 246, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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