Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59b6833a2bb046e86fa125b24f56a9613b6a6b80e7ef4ebcedde1a2983dbc5c6

Tx prefix hash: b0b89dd61fdf66959e4dbce58770410c0754b377b0549fba2ca397a13ddce12d
Tx public key: 7e0f45dcdb5aa523e84b1d76a897c566a5fc4da0b35a6d46328160a3238b59e8
Timestamp: 1588903201 Timestamp [UCT]: 2020-05-08 02:00:01 Age [y:d:h:m:s]: 05:181:01:55:02
Block: 99896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1304634 RingCT/type: yes/0
Extra: 017e0f45dcdb5aa523e84b1d76a897c566a5fc4da0b35a6d46328160a3238b59e80211000000e637fb5df4000000000000000000

1 output(s) for total of 286.420332954000 dcy

stealth address amount amount idx
00: edc0ed4e8e28c1a24ae2195ab64f62b4cdabd183d631e6c32a2a1667cbc357b6 286.420332954000 176078 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": 99906, "vin": [ { "gen": { "height": 99896 } } ], "vout": [ { "amount": 286420332954, "target": { "key": "edc0ed4e8e28c1a24ae2195ab64f62b4cdabd183d631e6c32a2a1667cbc357b6" } } ], "extra": [ 1, 126, 15, 69, 220, 219, 90, 165, 35, 232, 75, 29, 118, 168, 151, 197, 102, 165, 252, 77, 160, 179, 90, 109, 70, 50, 129, 96, 163, 35, 139, 89, 232, 2, 17, 0, 0, 0, 230, 55, 251, 93, 244, 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