Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8c44811b68c4b9dae656aeb5dda07580f026bffbe232f46a48cd361c6c272b4

Tx prefix hash: 2291e2ce8c57bfa811c0e6e314de90ad5c0ddb919ff573d35944c95bc59db0dd
Tx public key: d60090ccb5c89b1ea5849ef6c92ace18651ef2601eb015f209d5e8923841aa5b
Timestamp: 1740863570 Timestamp [UCT]: 2025-03-01 21:12:50 Age [y:d:h:m:s]: 00:264:14:49:05
Block: 1230062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186872 RingCT/type: yes/0
Extra: 01d60090ccb5c89b1ea5849ef6c92ace18651ef2601eb015f209d5e8923841aa5b0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fb146619f8d64c9c277ada973b7c2021116b692ff031da5103b706ed1ff4f0f 0.600000000000 1716957 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": 1230072, "vin": [ { "gen": { "height": 1230062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fb146619f8d64c9c277ada973b7c2021116b692ff031da5103b706ed1ff4f0f" } } ], "extra": [ 1, 214, 0, 144, 204, 181, 200, 155, 30, 165, 132, 158, 246, 201, 42, 206, 24, 101, 30, 242, 96, 30, 176, 21, 242, 9, 213, 232, 146, 56, 65, 170, 91, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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