Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d13a7ab99864c007acde8f88667caede9a1d0fb49c88be742d1c5a6448e4a680

Tx prefix hash: 7612656c7c68562fde30e23985576d9976104d19ca39b69f8021c3903e824268
Tx public key: 337a84a7d935ac3e1413c15e393e58a0c86f753ebdcf57dbf8e40dd85f12019c
Timestamp: 1574265417 Timestamp [UCT]: 2019-11-20 15:56:57 Age [y:d:h:m:s]: 05:007:22:26:59
Block: 13314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1148860 RingCT/type: yes/0
Extra: 01337a84a7d935ac3e1413c15e393e58a0c86f753ebdcf57dbf8e40dd85f12019c021100000001ccefb800000000000000000000

1 output(s) for total of 554.504494983000 dcy

stealth address amount amount idx
00: d845c8f182a177820369dde75ae2c1c14b0587d3db41d6c00c56d8824b55baa6 554.504494983000 15598 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": 13324, "vin": [ { "gen": { "height": 13314 } } ], "vout": [ { "amount": 554504494983, "target": { "key": "d845c8f182a177820369dde75ae2c1c14b0587d3db41d6c00c56d8824b55baa6" } } ], "extra": [ 1, 51, 122, 132, 167, 217, 53, 172, 62, 20, 19, 193, 94, 57, 62, 88, 160, 200, 111, 117, 62, 189, 207, 87, 219, 248, 228, 13, 216, 95, 18, 1, 156, 2, 17, 0, 0, 0, 1, 204, 239, 184, 0, 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