Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5af62fbb40a3a3fc3a7c36e50d903635104919dee175e68b6973846f3489e06

Tx prefix hash: d7df85c3d1a5a06b57875fefdf649fa62a7fcbd4b7e6edbbe8fce2cc63e4ec60
Tx public key: 8dff766f3ffd38407acf7c53d863a860dadfbc5d06918e20a9190b24223f892c
Timestamp: 1731371105 Timestamp [UCT]: 2024-11-12 00:25:05 Age [y:d:h:m:s]: 00:168:14:48:35
Block: 1151724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120377 RingCT/type: yes/0
Extra: 018dff766f3ffd38407acf7c53d863a860dadfbc5d06918e20a9190b24223f892c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 133c326ce9a4c1c086803fc3193ef027dab611c2349ec224fe18d2219859f3ce 0.600000000000 1637305 of 15

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": 1151734, "vin": [ { "gen": { "height": 1151724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "133c326ce9a4c1c086803fc3193ef027dab611c2349ec224fe18d2219859f3ce" } } ], "extra": [ 1, 141, 255, 118, 111, 63, 253, 56, 64, 122, 207, 124, 83, 216, 99, 168, 96, 218, 223, 188, 93, 6, 145, 142, 32, 169, 25, 11, 36, 34, 63, 137, 44, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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