Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b630173a4d70d967d3716cd37bb955810b98659b2849182633c954c636135cac

Tx prefix hash: 8f8ea5e2e19b99b3cc122994849923fc1bc1b6372158c3eff9e5cb611671f98e
Tx public key: df68b50b58d6292031a91bc1990dc815ecb51f3abdf7002642976e1047ee93df
Timestamp: 1700496364 Timestamp [UCT]: 2023-11-20 16:06:04 Age [y:d:h:m:s]: 01:062:09:14:14
Block: 895860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305946 RingCT/type: yes/0
Extra: 01df68b50b58d6292031a91bc1990dc815ecb51f3abdf7002642976e1047ee93df02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.660151965000 dcy

stealth address amount amount idx
00: c9a063f0031fbcf25e5725bb67b7eaf4d03f28bd99fc1ec2f2bc7ab3b8e13f65 0.660151965000 1352107 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": 895870, "vin": [ { "gen": { "height": 895860 } } ], "vout": [ { "amount": 660151965, "target": { "key": "c9a063f0031fbcf25e5725bb67b7eaf4d03f28bd99fc1ec2f2bc7ab3b8e13f65" } } ], "extra": [ 1, 223, 104, 181, 11, 88, 214, 41, 32, 49, 169, 27, 193, 153, 13, 200, 21, 236, 181, 31, 58, 189, 247, 0, 38, 66, 151, 110, 16, 71, 238, 147, 223, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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