Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ade5a3aad461b3c89c642e165c2249b2d7ba9864c8d4068f97863cb29a91d8d

Tx prefix hash: 991e187c50a882dd0ea0d068ad3d2df55bb11316c088962d6f70581b34704538
Tx public key: a6f3bf1fcc3a3ae53b68452fa1206c4255bbc6d3a171755fdda6770d80de6ae7
Timestamp: 1722332469 Timestamp [UCT]: 2024-07-30 09:41:09 Age [y:d:h:m:s]: 00:242:20:39:26
Block: 1076898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173466 RingCT/type: yes/0
Extra: 01a6f3bf1fcc3a3ae53b68452fa1206c4255bbc6d3a171755fdda6770d80de6ae702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a848af06ddf8969efad7bf736acc68e362e32765d6d557c8e3af90e025b6efe1 0.600000000000 1549441 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": 1076908, "vin": [ { "gen": { "height": 1076898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a848af06ddf8969efad7bf736acc68e362e32765d6d557c8e3af90e025b6efe1" } } ], "extra": [ 1, 166, 243, 191, 31, 204, 58, 58, 229, 59, 104, 69, 47, 161, 32, 108, 66, 85, 187, 198, 211, 161, 113, 117, 95, 221, 166, 119, 13, 128, 222, 106, 231, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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