Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25a469ef581b4fb15fdfaf667ccff6e0863231bf9fdca656a64fffe543a710cc

Tx prefix hash: cf108a78858e6491677109fd4a2a3de85705801e1bf19df93c2f317108ec3336
Tx public key: a96c8cbee2975a281c9970ac7e7eb5508ca028bca0e7fff358fba3413029c694
Timestamp: 1712202488 Timestamp [UCT]: 2024-04-04 03:48:08 Age [y:d:h:m:s]: 00:280:01:14:28
Block: 992878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200491 RingCT/type: yes/0
Extra: 01a96c8cbee2975a281c9970ac7e7eb5508ca028bca0e7fff358fba3413029c6940211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 027dd738544579c89d33675f6e00a275d194bc6c3a9f3a4ac01bd4a71c83b0b9 0.600000000000 1453254 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": 992888, "vin": [ { "gen": { "height": 992878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "027dd738544579c89d33675f6e00a275d194bc6c3a9f3a4ac01bd4a71c83b0b9" } } ], "extra": [ 1, 169, 108, 140, 190, 226, 151, 90, 40, 28, 153, 112, 172, 126, 126, 181, 80, 140, 160, 40, 188, 160, 231, 255, 243, 88, 251, 163, 65, 48, 41, 198, 148, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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