Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ef3fdcd622415bea7332b2a3024072fa36ef38d5f59464ce683482cab3986ee

Tx prefix hash: d880f6bbe1c3f80d109bbd3ecd6c47801e017a6cc335259a80e4a7ccd87ec258
Tx public key: a9d7d61fb8a6b7eab85501ace96232b538c3c00d24686f7a1b1fa5b129465c04
Timestamp: 1712671625 Timestamp [UCT]: 2024-04-09 14:07:05 Age [y:d:h:m:s]: 01:213:05:34:51
Block: 996773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411091 RingCT/type: yes/0
Extra: 01a9d7d61fb8a6b7eab85501ace96232b538c3c00d24686f7a1b1fa5b129465c0402110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c2ee8bd6daca368851430f1d24c748f55e271fa339703934b9ce5270d855906 0.600000000000 1457201 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": 996783, "vin": [ { "gen": { "height": 996773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c2ee8bd6daca368851430f1d24c748f55e271fa339703934b9ce5270d855906" } } ], "extra": [ 1, 169, 215, 214, 31, 184, 166, 183, 234, 184, 85, 1, 172, 233, 98, 50, 181, 56, 195, 192, 13, 36, 104, 111, 122, 27, 31, 165, 177, 41, 70, 92, 4, 2, 17, 0, 0, 0, 7, 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