Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b8f9a1436ebe3f45583d0050f58c7da510f9c81e553500eab3f52d8f50a248d

Tx prefix hash: 50fd7227e7302a023ea052f6d782064d40e9ed2b924ca18be627262f3e52559c
Tx public key: 557737d39cb82c1c2b020623b339a452c7628aebd9eea5d7df6440a2d17e89af
Timestamp: 1583768085 Timestamp [UCT]: 2020-03-09 15:34:45 Age [y:d:h:m:s]: 05:214:09:39:53
Block: 79533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1306304 RingCT/type: yes/0
Extra: 01557737d39cb82c1c2b020623b339a452c7628aebd9eea5d7df6440a2d17e89af0211000000064943cd9f000000000000000000

1 output(s) for total of 334.566486767000 dcy

stealth address amount amount idx
00: 24dce309aeb0207108d736d2dc03fb0d251df4581964dbd5e3a0b146f90f1ab9 334.566486767000 145495 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": 79543, "vin": [ { "gen": { "height": 79533 } } ], "vout": [ { "amount": 334566486767, "target": { "key": "24dce309aeb0207108d736d2dc03fb0d251df4581964dbd5e3a0b146f90f1ab9" } } ], "extra": [ 1, 85, 119, 55, 211, 156, 184, 44, 28, 43, 2, 6, 35, 179, 57, 164, 82, 199, 98, 138, 235, 217, 238, 165, 215, 223, 100, 64, 162, 209, 126, 137, 175, 2, 17, 0, 0, 0, 6, 73, 67, 205, 159, 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