Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68e069c818c2c5eaa507f8a89d76de668ab9d70536033c9a84901efb1ef0c40d

Tx prefix hash: 64cf87ee3e6f927f48e7041aa736dcfa9e2ea69c78af5bfdfa3f9a310e6834c1
Tx public key: 8589f7f24a14fa6392af4573df6f74a144dc06ddad031f9e6ce7e39bef820b22
Timestamp: 1577386032 Timestamp [UCT]: 2019-12-26 18:47:12 Age [y:d:h:m:s]: 05:007:22:19:00
Block: 32397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155615 RingCT/type: yes/0
Extra: 018589f7f24a14fa6392af4573df6f74a144dc06ddad031f9e6ce7e39bef820b22021100000067398c17aa000000000000000000

1 output(s) for total of 479.353771985000 dcy

stealth address amount amount idx
00: 0efc7d488bc4e0f1bcbb49eab3a14730c49f4f0c5a30b349bfa68a67a607064f 479.353771985000 53862 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": 32407, "vin": [ { "gen": { "height": 32397 } } ], "vout": [ { "amount": 479353771985, "target": { "key": "0efc7d488bc4e0f1bcbb49eab3a14730c49f4f0c5a30b349bfa68a67a607064f" } } ], "extra": [ 1, 133, 137, 247, 242, 74, 20, 250, 99, 146, 175, 69, 115, 223, 111, 116, 161, 68, 220, 6, 221, 173, 3, 31, 158, 108, 231, 227, 155, 239, 130, 11, 34, 2, 17, 0, 0, 0, 103, 57, 140, 23, 170, 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