Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f82609b6d846b72ea47488a105a2b1bfd5aa24648f7c9371105f74ad90c42bd

Tx prefix hash: 0cf9cbca99fc8c2d209b3ab60e74a463225c44ac1ef50678ea45006edd381e68
Tx public key: 88acb2ca92267cb0e8c6f9492f4fdcc6b043fd41f193adf033ccdfe437980147
Timestamp: 1734011759 Timestamp [UCT]: 2024-12-12 13:55:59 Age [y:d:h:m:s]: 00:115:02:04:34
Block: 1173633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82018 RingCT/type: yes/0
Extra: 0188acb2ca92267cb0e8c6f9492f4fdcc6b043fd41f193adf033ccdfe437980147021100000005a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46ea2b203bab4f002890f30ca40a0eff35a4bbd2347b82703bae1b82c137d8b1 0.600000000000 1659678 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": 1173643, "vin": [ { "gen": { "height": 1173633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46ea2b203bab4f002890f30ca40a0eff35a4bbd2347b82703bae1b82c137d8b1" } } ], "extra": [ 1, 136, 172, 178, 202, 146, 38, 124, 176, 232, 198, 249, 73, 47, 79, 220, 198, 176, 67, 253, 65, 241, 147, 173, 240, 51, 204, 223, 228, 55, 152, 1, 71, 2, 17, 0, 0, 0, 5, 162, 215, 95, 68, 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