Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d12498ee5525955ab75dec0f47b18f2c4fb762ed9036f603e052e1be76467b1

Tx prefix hash: 84d9e69ef865762c4bb76ed840faebb5fb7d89951c1f0fa6b32bacd955b0ac42
Tx public key: 0b02ed72123f7eedd3635bf0c584c95cf74b5a0a388c2bf6d5435134bcf465e1
Timestamp: 1646763308 Timestamp [UCT]: 2022-03-08 18:15:08 Age [y:d:h:m:s]: 02:290:05:17:24
Block: 454140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 726943 RingCT/type: yes/0
Extra: 010b02ed72123f7eedd3635bf0c584c95cf74b5a0a388c2bf6d5435134bcf465e10211000000134da16a3a000000000000000000

1 output(s) for total of 19.197555430000 dcy

stealth address amount amount idx
00: e563cc0100d4ca3608a67b515a4f217e971a87f174a3c9745d84d0d147e873a1 19.197555430000 869733 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": 454150, "vin": [ { "gen": { "height": 454140 } } ], "vout": [ { "amount": 19197555430, "target": { "key": "e563cc0100d4ca3608a67b515a4f217e971a87f174a3c9745d84d0d147e873a1" } } ], "extra": [ 1, 11, 2, 237, 114, 18, 63, 126, 237, 211, 99, 91, 240, 197, 132, 201, 92, 247, 75, 90, 10, 56, 140, 43, 246, 213, 67, 81, 52, 188, 244, 101, 225, 2, 17, 0, 0, 0, 19, 77, 161, 106, 58, 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