Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9105ce7a5b8d637da52b9e3fa25b0a507caa6ed09843d15d80259151a3cf65f

Tx prefix hash: 6412e585514c8174370663c5c200131a2f79d183bf8e6748f932787622c5d644
Tx public key: d09f6293bf88c823e4d5e16f125f366d370ecc22325c512c729e0b3f29ebc251
Timestamp: 1725514639 Timestamp [UCT]: 2024-09-05 05:37:19 Age [y:d:h:m:s]: 00:125:22:50:07
Block: 1103274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90077 RingCT/type: yes/0
Extra: 01d09f6293bf88c823e4d5e16f125f366d370ecc22325c512c729e0b3f29ebc25102110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: babd33e17130ce95449cb29ac9b1a50988a41acf273d52b4d367c6b233a6cdb4 0.600000000000 1580041 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": 1103284, "vin": [ { "gen": { "height": 1103274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "babd33e17130ce95449cb29ac9b1a50988a41acf273d52b4d367c6b233a6cdb4" } } ], "extra": [ 1, 208, 159, 98, 147, 191, 136, 200, 35, 228, 213, 225, 111, 18, 95, 54, 109, 55, 14, 204, 34, 50, 92, 81, 44, 114, 158, 11, 63, 41, 235, 194, 81, 2, 17, 0, 0, 0, 12, 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