Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa639ba9d56d3081a5e093caf127066dcbdc60534f2971739ed96179fb8b7415

Tx prefix hash: bb956a150d10f4baf18baa2d9c38e1d4adec1c70d812a1ec00b7dd3e8c5cded3
Tx public key: e2113e10b085562f19310e6b12782f0d026c8ec58deac4248ed43496023528d6
Timestamp: 1582100528 Timestamp [UCT]: 2020-02-19 08:22:08 Age [y:d:h:m:s]: 04:131:20:34:19
Block: 67997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 986545 RingCT/type: yes/0
Extra: 01e2113e10b085562f19310e6b12782f0d026c8ec58deac4248ed43496023528d602110000000203d36d11000000000000000000

1 output(s) for total of 365.341088783000 dcy

stealth address amount amount idx
00: a9eedd728a32a4823745b0c0c535ddf5e202eb6f3cc25e0fa39fb25156693a8c 365.341088783000 125257 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": 68007, "vin": [ { "gen": { "height": 67997 } } ], "vout": [ { "amount": 365341088783, "target": { "key": "a9eedd728a32a4823745b0c0c535ddf5e202eb6f3cc25e0fa39fb25156693a8c" } } ], "extra": [ 1, 226, 17, 62, 16, 176, 133, 86, 47, 25, 49, 14, 107, 18, 120, 47, 13, 2, 108, 142, 197, 141, 234, 196, 36, 142, 212, 52, 150, 2, 53, 40, 214, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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