Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91f890943c69b08015cfcbca2c8f0d7deb0ec574d799811b381af4d6cba23437

Tx prefix hash: e546e9a0102d944593606537363e0a4ad60c647aa8f0aa77fde31611839a3945
Tx public key: 096775a73d75246b7d31d1764cd2957e85a24be9efd8c5132cb4ecc5226e53f0
Timestamp: 1706254905 Timestamp [UCT]: 2024-01-26 07:41:45 Age [y:d:h:m:s]: 01:030:14:02:38
Block: 943575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282920 RingCT/type: yes/0
Extra: 01096775a73d75246b7d31d1764cd2957e85a24be9efd8c5132cb4ecc5226e53f002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3d01b5b6aea943519da9447a5464b358e798fe600d29f1180c2ed33feeba207 0.600000000000 1401783 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": 943585, "vin": [ { "gen": { "height": 943575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3d01b5b6aea943519da9447a5464b358e798fe600d29f1180c2ed33feeba207" } } ], "extra": [ 1, 9, 103, 117, 167, 61, 117, 36, 107, 125, 49, 209, 118, 76, 210, 149, 126, 133, 162, 75, 233, 239, 216, 197, 19, 44, 180, 236, 197, 34, 110, 83, 240, 2, 17, 0, 0, 0, 3, 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