Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a83a5e3dc9bf99ed392ceb99fc66dcc534bda5ee9027dd83a886c22adc715024

Tx prefix hash: e3349229e8ed82e8433ccf1e6de9cc56b1bf80b254207aeb7a22778d34f87111
Tx public key: 97cdbb631fc0cd3f7ddbc28bd9d47cf77848dbbbb6e5a8164c3b8bd5e5d6c5f6
Timestamp: 1716069582 Timestamp [UCT]: 2024-05-18 21:59:42 Age [y:d:h:m:s]: 00:321:20:22:53
Block: 1024967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230049 RingCT/type: yes/0
Extra: 0197cdbb631fc0cd3f7ddbc28bd9d47cf77848dbbbb6e5a8164c3b8bd5e5d6c5f602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 509283d2d9c1110f131ecde15259a152ea31c950fe18f5408a7f4d04576ad6b0 0.600000000000 1491124 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": 1024977, "vin": [ { "gen": { "height": 1024967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "509283d2d9c1110f131ecde15259a152ea31c950fe18f5408a7f4d04576ad6b0" } } ], "extra": [ 1, 151, 205, 187, 99, 31, 192, 205, 63, 125, 219, 194, 139, 217, 212, 124, 247, 120, 72, 219, 187, 182, 229, 168, 22, 76, 59, 139, 213, 229, 214, 197, 246, 2, 17, 0, 0, 0, 1, 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