Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f840e00ffe5110b6d0ad7948b6bf4ab33d4cf37c59341b0acbe57c2b696659da

Tx prefix hash: 4e6c58f08d6c2ecb2798779b197c0c2611c4c8e27d1dd1dfd0603cbc6f975b61
Tx public key: b14a8e3ce992b69ff96ce59555d2dfcdd729325a1eacf99516cd44d9e2428fdd
Timestamp: 1578743234 Timestamp [UCT]: 2020-01-11 11:47:14 Age [y:d:h:m:s]: 05:135:23:34:08
Block: 43219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1247362 RingCT/type: yes/0
Extra: 01b14a8e3ce992b69ff96ce59555d2dfcdd729325a1eacf99516cd44d9e2428fdd0211000000048a2ee0d9000000000000000000

1 output(s) for total of 441.408401532000 dcy

stealth address amount amount idx
00: 5cfdcecf2088365f0a0fe44dd2caf72ddb4eacfa40a9f7e465f13c0e0ecaf354 441.408401532000 78166 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": 43229, "vin": [ { "gen": { "height": 43219 } } ], "vout": [ { "amount": 441408401532, "target": { "key": "5cfdcecf2088365f0a0fe44dd2caf72ddb4eacfa40a9f7e465f13c0e0ecaf354" } } ], "extra": [ 1, 177, 74, 142, 60, 233, 146, 182, 159, 249, 108, 229, 149, 85, 210, 223, 205, 215, 41, 50, 90, 30, 172, 249, 149, 22, 205, 68, 217, 226, 66, 143, 221, 2, 17, 0, 0, 0, 4, 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