Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cae1c137b25436f1d66b4fc959a4053d8a2f66be96c65a5c48d92b2fb4868f3

Tx prefix hash: 8fc1525837e19ae2b49e12780cb07278ca2cca7e5d5c5f3dbf9451c065d04607
Tx public key: cc8345bd209a68937f8942fc92d56b6e3f13f921557b6bebaeda59333e6cd5ae
Timestamp: 1723746446 Timestamp [UCT]: 2024-08-15 18:27:26 Age [y:d:h:m:s]: 00:249:20:11:28
Block: 1088611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178447 RingCT/type: yes/0
Extra: 01cc8345bd209a68937f8942fc92d56b6e3f13f921557b6bebaeda59333e6cd5ae021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 263c414608ae07e974765abeb60a88e7f68b188f0ddb6c003f9eeae2938c949a 0.600000000000 1563228 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": 1088621, "vin": [ { "gen": { "height": 1088611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "263c414608ae07e974765abeb60a88e7f68b188f0ddb6c003f9eeae2938c949a" } } ], "extra": [ 1, 204, 131, 69, 189, 32, 154, 104, 147, 127, 137, 66, 252, 146, 213, 107, 110, 63, 19, 249, 33, 85, 123, 107, 235, 174, 218, 89, 51, 62, 108, 213, 174, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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