Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2cf311fee52b425655823f0defb4f69da3f91c522e686025400f01416d0ace6

Tx prefix hash: 775e52174aaae9886bd7d6dadbb215667addefa47ae26aeca0c81794f2ca3121
Tx public key: bd99f2b7a24dbbb92ba8b470ecc51a7371de59b73fc31e8d3316d4e2ffda5269
Timestamp: 1765980334 Timestamp [UCT]: 2025-12-17 14:05:34 Age [y:d:h:m:s]: 00:004:20:50:54
Block: 1435614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3487 RingCT/type: yes/0
Extra: 01bd99f2b7a24dbbb92ba8b470ecc51a7371de59b73fc31e8d3316d4e2ffda526902110000000a70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6822faf80fd60d926a919b04eac7d68c87f916cb1f5bd3144f81c24382a10e10 0.600000000000 1924411 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": 1435624, "vin": [ { "gen": { "height": 1435614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6822faf80fd60d926a919b04eac7d68c87f916cb1f5bd3144f81c24382a10e10" } } ], "extra": [ 1, 189, 153, 242, 183, 162, 77, 187, 185, 43, 168, 180, 112, 236, 197, 26, 115, 113, 222, 89, 183, 63, 195, 30, 141, 51, 22, 212, 226, 255, 218, 82, 105, 2, 17, 0, 0, 0, 10, 112, 96, 157, 3, 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