Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfb4c610cda071dfe4f0a7e86ab70c055a833947109e1b83710ac99de08b83af

Tx prefix hash: 5829bd3e9f1081db8f37e5b18f442e1d59032ed3a9ceeca85d6a2aed92cd588a
Tx public key: 445a39beae73c667454a218bd5ad7924249f2a11dce7c6cf75eeeeaacc61e8b0
Timestamp: 1733327695 Timestamp [UCT]: 2024-12-04 15:54:55 Age [y:d:h:m:s]: 00:193:02:48:59
Block: 1167942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137771 RingCT/type: yes/0
Extra: 01445a39beae73c667454a218bd5ad7924249f2a11dce7c6cf75eeeeaacc61e8b002110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32e7d791b5ccc75165c990cd3116c0c9df5edda0b2873cf96c24ebcc8a2cc16c 0.600000000000 1653647 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": 1167952, "vin": [ { "gen": { "height": 1167942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32e7d791b5ccc75165c990cd3116c0c9df5edda0b2873cf96c24ebcc8a2cc16c" } } ], "extra": [ 1, 68, 90, 57, 190, 174, 115, 198, 103, 69, 74, 33, 139, 213, 173, 121, 36, 36, 159, 42, 17, 220, 231, 198, 207, 117, 238, 238, 170, 204, 97, 232, 176, 2, 17, 0, 0, 0, 11, 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