Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd9e2d833bb61a979d2c718b32004469e8faa19a3ca8b52f664ad6cfb578e188

Tx prefix hash: 6022f8a089646eb2099f64941c564f957243fbb844514d78cd9d122a1096ded8
Tx public key: 9c0852b15d43f301cde8fbe59d7f9c5110c6c17ac40544514963ccd03ee42dce
Timestamp: 1657298915 Timestamp [UCT]: 2022-07-08 16:48:35 Age [y:d:h:m:s]: 02:255:05:23:02
Block: 539441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 703554 RingCT/type: yes/0
Extra: 019c0852b15d43f301cde8fbe59d7f9c5110c6c17ac40544514963ccd03ee42dce02110000001ea8c141c5000000000000000000

1 output(s) for total of 10.014013721000 dcy

stealth address amount amount idx
00: 9eef77c33ca0af3ef0fd8839b593467e4f53275f045d48ff43b4f0eec08a0b84 10.014013721000 969544 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": 539451, "vin": [ { "gen": { "height": 539441 } } ], "vout": [ { "amount": 10014013721, "target": { "key": "9eef77c33ca0af3ef0fd8839b593467e4f53275f045d48ff43b4f0eec08a0b84" } } ], "extra": [ 1, 156, 8, 82, 177, 93, 67, 243, 1, 205, 232, 251, 229, 157, 127, 156, 81, 16, 198, 193, 122, 196, 5, 68, 81, 73, 99, 204, 208, 62, 228, 45, 206, 2, 17, 0, 0, 0, 30, 168, 193, 65, 197, 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