Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e1d1514d2861938af74e43c62606a417e2628ffc8737cd8a4db556505ec1046

Tx prefix hash: 8892eb3a37f667cde7759d7a086e25abb8ad324aff0123cd6a6d2e518ec3d2d7
Tx public key: b6337ee7a99050db47e5857b404a665a821f1e52b5b03e67af8039deca8683d1
Timestamp: 1713301457 Timestamp [UCT]: 2024-04-16 21:04:17 Age [y:d:h:m:s]: 00:267:05:05:57
Block: 1002004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191282 RingCT/type: yes/0
Extra: 01b6337ee7a99050db47e5857b404a665a821f1e52b5b03e67af8039deca8683d102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9676b7c931b1bbc7c654ae585876a610174a8da53b46defa1c5d65bd2f8d9c0 0.600000000000 1462518 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": 1002014, "vin": [ { "gen": { "height": 1002004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9676b7c931b1bbc7c654ae585876a610174a8da53b46defa1c5d65bd2f8d9c0" } } ], "extra": [ 1, 182, 51, 126, 231, 169, 144, 80, 219, 71, 229, 133, 123, 64, 74, 102, 90, 130, 31, 30, 82, 181, 176, 62, 103, 175, 128, 57, 222, 202, 134, 131, 209, 2, 17, 0, 0, 0, 5, 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