Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddfc41d36f3e576c8b62b20e6ca7869384257a2c26539c3d91d03535c38d24db

Tx prefix hash: d4f79d02b51be9f74b6b79fab885f5689f1e73180090625e6fe4430300dd05f6
Tx public key: e5eb031408a74536a96a4fe6672041c07b8c586dcfc85faac86f8aa018b0a9d4
Timestamp: 1703775041 Timestamp [UCT]: 2023-12-28 14:50:41 Age [y:d:h:m:s]: 01:105:20:39:58
Block: 923039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336779 RingCT/type: yes/0
Extra: 01e5eb031408a74536a96a4fe6672041c07b8c586dcfc85faac86f8aa018b0a9d402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 855550909a838a3bfc906a6bb03d98ddb1e941904c4b451b3d9ecce31c1a268d 0.600000000000 1380753 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": 923049, "vin": [ { "gen": { "height": 923039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "855550909a838a3bfc906a6bb03d98ddb1e941904c4b451b3d9ecce31c1a268d" } } ], "extra": [ 1, 229, 235, 3, 20, 8, 167, 69, 54, 169, 106, 79, 230, 103, 32, 65, 192, 123, 140, 88, 109, 207, 200, 95, 170, 200, 111, 138, 160, 24, 176, 169, 212, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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