Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 136fbbd7ef069e250832ca924c8de90b6331b9e1ce1cd160ddd38308ade472a1

Tx prefix hash: 1fc1cecd9a70b54e9c826a01f9c8eeea5a85575a486f4a2265b5999e92cb6b9d
Tx public key: 14c8d914e0717eb0edfa44f42e13fa74505ca1817fceed4ea084cf378eed3ea9
Timestamp: 1704610006 Timestamp [UCT]: 2024-01-07 06:46:46 Age [y:d:h:m:s]: 01:143:10:46:14
Block: 929940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363689 RingCT/type: yes/0
Extra: 0114c8d914e0717eb0edfa44f42e13fa74505ca1817fceed4ea084cf378eed3ea902110000000441ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ea0d07a79a7e8e55122d7350eb3e1fc1648085aff88eb29a1b4b91f2b47938c 0.600000000000 1387818 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": 929950, "vin": [ { "gen": { "height": 929940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ea0d07a79a7e8e55122d7350eb3e1fc1648085aff88eb29a1b4b91f2b47938c" } } ], "extra": [ 1, 20, 200, 217, 20, 224, 113, 126, 176, 237, 250, 68, 244, 46, 19, 250, 116, 80, 92, 161, 129, 127, 206, 237, 78, 160, 132, 207, 55, 142, 237, 62, 169, 2, 17, 0, 0, 0, 4, 65, 238, 28, 155, 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