Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c671fa58f712fd0ea1f845a68fb9997c12f317fb3f0f3be3017346570513b73

Tx prefix hash: 3e8da60aed11e6480ba2f9b0f989e490907d0e70b1124df8bcfc264260758527
Tx public key: 3f609a799af8ee06159ab0dae89928bd9bfea2071940cc587562cf787c2e9d64
Timestamp: 1582487232 Timestamp [UCT]: 2020-02-23 19:47:12 Age [y:d:h:m:s]: 04:308:10:38:33
Block: 70961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113154 RingCT/type: yes/0
Extra: 013f609a799af8ee06159ab0dae89928bd9bfea2071940cc587562cf787c2e9d64021100000008d81c26c0000000000000000000

1 output(s) for total of 357.172120334000 dcy

stealth address amount amount idx
00: e225a4dfd62bddfbed634adbb3b10c250fd96a614cb9695a4488e1d5b7c3ff56 357.172120334000 131164 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": 70971, "vin": [ { "gen": { "height": 70961 } } ], "vout": [ { "amount": 357172120334, "target": { "key": "e225a4dfd62bddfbed634adbb3b10c250fd96a614cb9695a4488e1d5b7c3ff56" } } ], "extra": [ 1, 63, 96, 154, 121, 154, 248, 238, 6, 21, 154, 176, 218, 232, 153, 40, 189, 155, 254, 162, 7, 25, 64, 204, 88, 117, 98, 207, 120, 124, 46, 157, 100, 2, 17, 0, 0, 0, 8, 216, 28, 38, 192, 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