Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c214d509527e3463512402939b190df543b5ac534e0196a6520dda6bc160d4d8

Tx prefix hash: ad89e05aee05951b64684023c18438f7b6f1cd2713686f754f5f21f79a7aa9f1
Tx public key: d6c010c5787079a07e2485b2e0c0b49e66028a5c312bceab03befb4f99eff90f
Timestamp: 1713464170 Timestamp [UCT]: 2024-04-18 18:16:10 Age [y:d:h:m:s]: 01:222:19:32:30
Block: 1003353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417940 RingCT/type: yes/0
Extra: 01d6c010c5787079a07e2485b2e0c0b49e66028a5c312bceab03befb4f99eff90f02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f3e1bc9539daf2cf4bae10c30a1fcbec685c6f96cd161e86ec0bbead73773bb 0.600000000000 1463883 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": 1003363, "vin": [ { "gen": { "height": 1003353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f3e1bc9539daf2cf4bae10c30a1fcbec685c6f96cd161e86ec0bbead73773bb" } } ], "extra": [ 1, 214, 192, 16, 197, 120, 112, 121, 160, 126, 36, 133, 178, 224, 192, 180, 158, 102, 2, 138, 92, 49, 43, 206, 171, 3, 190, 251, 79, 153, 239, 249, 15, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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