Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a47f8c7fe12d90b7ec79b81c5bdb9fc5b914653e959a3e9a79e3e28e619444a1

Tx prefix hash: 5d7d4200e05a9c04e4c6bd7629d2e68ac5759652238a8aa8878680d3ee91fce5
Tx public key: 40905d0ed1841f2d8e125799df56851b36e5feb40edaa1d091d3ab5bf3910fa1
Timestamp: 1734025153 Timestamp [UCT]: 2024-12-12 17:39:13 Age [y:d:h:m:s]: 00:113:17:47:51
Block: 1173745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81065 RingCT/type: yes/0
Extra: 0140905d0ed1841f2d8e125799df56851b36e5feb40edaa1d091d3ab5bf3910fa10211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2d93d8f9e72c765e81b9c40a52d7448498894583c53f47514dbd4b8e8cee69c 0.600000000000 1659800 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": 1173755, "vin": [ { "gen": { "height": 1173745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2d93d8f9e72c765e81b9c40a52d7448498894583c53f47514dbd4b8e8cee69c" } } ], "extra": [ 1, 64, 144, 93, 14, 209, 132, 31, 45, 142, 18, 87, 153, 223, 86, 133, 27, 54, 229, 254, 180, 14, 218, 161, 208, 145, 211, 171, 91, 243, 145, 15, 161, 2, 17, 0, 0, 0, 7, 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