Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58e61f52184774c642377c4f5a698b4c0fb7acbddacd6ba49d7b9583e2df635b

Tx prefix hash: 2356312d571e4cbb57d5a032515e0999758037522a2546ccb1a84b2b9e8518b0
Tx public key: 7aeda05c0cf9d87e52cedc62e4cd58b18db562b6fa5e30839b401fd547c0d505
Timestamp: 1582105719 Timestamp [UCT]: 2020-02-19 09:48:39 Age [y:d:h:m:s]: 04:283:20:05:08
Block: 68069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1095280 RingCT/type: yes/0
Extra: 017aeda05c0cf9d87e52cedc62e4cd58b18db562b6fa5e30839b401fd547c0d5050211000000014ac5aa02000000000000000000

1 output(s) for total of 365.140455274000 dcy

stealth address amount amount idx
00: 2238e9b8090a39c575cecc0049856e0f5d5c7694f9fa95b08259c8cbf623a70e 365.140455274000 125419 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": 68079, "vin": [ { "gen": { "height": 68069 } } ], "vout": [ { "amount": 365140455274, "target": { "key": "2238e9b8090a39c575cecc0049856e0f5d5c7694f9fa95b08259c8cbf623a70e" } } ], "extra": [ 1, 122, 237, 160, 92, 12, 249, 216, 126, 82, 206, 220, 98, 228, 205, 88, 177, 141, 181, 98, 182, 250, 94, 48, 131, 155, 64, 31, 213, 71, 192, 213, 5, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 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