Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dce3ef4b36e17e0e8f624335987cc7fff8f2782db45478cec85eb1f502021df

Tx prefix hash: b69a92f69f1ee51e04b3087e7bf9655f89d7c96d8654275779e8da5e4f784c27
Tx public key: 0d444c094429d1dd9e93f6c9703c75a39ca8c651626065d71b440816f0757087
Timestamp: 1697296756 Timestamp [UCT]: 2023-10-14 15:19:16 Age [y:d:h:m:s]: 01:109:21:16:46
Block: 869532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339539 RingCT/type: yes/0
Extra: 010d444c094429d1dd9e93f6c9703c75a39ca8c651626065d71b440816f075708702110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.807011181000 dcy

stealth address amount amount idx
00: f5a000a040fbd62690b4fbcf5689fa7683f9239d46dd8859d2f92479f8308433 0.807011181000 1324379 of 0

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": 869542, "vin": [ { "gen": { "height": 869532 } } ], "vout": [ { "amount": 807011181, "target": { "key": "f5a000a040fbd62690b4fbcf5689fa7683f9239d46dd8859d2f92479f8308433" } } ], "extra": [ 1, 13, 68, 76, 9, 68, 41, 209, 221, 158, 147, 246, 201, 112, 60, 117, 163, 156, 168, 198, 81, 98, 96, 101, 215, 27, 68, 8, 22, 240, 117, 112, 135, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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