Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8eb8540fb0d293696ee35aad0c5b50e92bcaf901fef38ce036a937124a1a185f

Tx prefix hash: 3bb555d251115e1edf0aa51054b7efd8ee1515cfe99196abee7dd7625b2c01af
Tx public key: 075f80bbb9e80f5d0540ad0f18e1e57c238acb1cdc42e9912e1124763735e90a
Timestamp: 1574618919 Timestamp [UCT]: 2019-11-24 18:08:39 Age [y:d:h:m:s]: 05:073:00:23:45
Block: 16606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194772 RingCT/type: yes/0
Extra: 01075f80bbb9e80f5d0540ad0f18e1e57c238acb1cdc42e9912e1124763735e90a021100000004b63f0b49000000000000000000

1 output(s) for total of 540.798117092000 dcy

stealth address amount amount idx
00: 32cc010b27fcb0a3764813149bb8bd9b55235c86f8502dfe9719ea58c4d40004 540.798117092000 23348 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": 16616, "vin": [ { "gen": { "height": 16606 } } ], "vout": [ { "amount": 540798117092, "target": { "key": "32cc010b27fcb0a3764813149bb8bd9b55235c86f8502dfe9719ea58c4d40004" } } ], "extra": [ 1, 7, 95, 128, 187, 185, 232, 15, 93, 5, 64, 173, 15, 24, 225, 229, 124, 35, 138, 203, 28, 220, 66, 233, 145, 46, 17, 36, 118, 55, 53, 233, 10, 2, 17, 0, 0, 0, 4, 182, 63, 11, 73, 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