Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5db1a2f65e18236dfdedd004212af0fe61831b0646de8999e59cf602144d565d

Tx prefix hash: 8b1d148191530e1e284b099af1bec851efd5ded598af607046d7f53b8074853f
Tx public key: 1ab04cde87996f9a4f533b1bfd2e108548ae7e8324b3d543aae35b1d781c70b4
Timestamp: 1585418021 Timestamp [UCT]: 2020-03-28 17:53:41 Age [y:d:h:m:s]: 04:286:19:38:00
Block: 89022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103891 RingCT/type: yes/0
Extra: 011ab04cde87996f9a4f533b1bfd2e108548ae7e8324b3d543aae35b1d781c70b4021100000035209b4bc8000000000000000000

1 output(s) for total of 311.195949732000 dcy

stealth address amount amount idx
00: fd6d54013e35d9c5b7547c0dad2738431b6cdb36a1e45e7b8e666aa4b6f1c9db 311.195949732000 159870 of 0

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": 89032, "vin": [ { "gen": { "height": 89022 } } ], "vout": [ { "amount": 311195949732, "target": { "key": "fd6d54013e35d9c5b7547c0dad2738431b6cdb36a1e45e7b8e666aa4b6f1c9db" } } ], "extra": [ 1, 26, 176, 76, 222, 135, 153, 111, 154, 79, 83, 59, 27, 253, 46, 16, 133, 72, 174, 126, 131, 36, 179, 213, 67, 170, 227, 91, 29, 120, 28, 112, 180, 2, 17, 0, 0, 0, 53, 32, 155, 75, 200, 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