Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a337bfd2ef21f07702b96f613053bd6f1fb309fd14c872084f886eb1053ddeea

Tx prefix hash: 3b99ab0c1eea2226d68615bb8cd085d92261f4ac98fc5e188ede8aa6700640b5
Tx public key: b077c3f51c116b2e5ace6018a6142c57f2cc5f7f7fc5a8cb092950e8a9f38c28
Timestamp: 1579437080 Timestamp [UCT]: 2020-01-19 12:31:20 Age [y:d:h:m:s]: 05:051:23:09:23
Block: 48941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1187293 RingCT/type: yes/0
Extra: 01b077c3f51c116b2e5ace6018a6142c57f2cc5f7f7fc5a8cb092950e8a9f38c280211000000078a2ee0d9000000000000000000

1 output(s) for total of 422.511938764000 dcy

stealth address amount amount idx
00: 2317b80268cc4099b8e93f48831d3ba1adfa7f1a72794c651a5ab3f3f495bf54 422.511938764000 90783 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": 48951, "vin": [ { "gen": { "height": 48941 } } ], "vout": [ { "amount": 422511938764, "target": { "key": "2317b80268cc4099b8e93f48831d3ba1adfa7f1a72794c651a5ab3f3f495bf54" } } ], "extra": [ 1, 176, 119, 195, 245, 28, 17, 107, 46, 90, 206, 96, 24, 166, 20, 44, 87, 242, 204, 95, 127, 127, 197, 168, 203, 9, 41, 80, 232, 169, 243, 140, 40, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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