Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be9228741337b1cfc576789a7a0f7a961a0ce6c926391173fe4ae3a7f6db7a7f

Tx prefix hash: 9a4b3b0a666912bca5f399693517fbfabfebb954dc487ac2eb84e51360561162
Tx public key: c225b702b8008135e903523393d657d0aa5897e80a25f55b3c45cf2764c9b3ff
Timestamp: 1732144430 Timestamp [UCT]: 2024-11-20 23:13:50 Age [y:d:h:m:s]: 00:003:14:45:10
Block: 1158134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2600 RingCT/type: yes/0
Extra: 01c225b702b8008135e903523393d657d0aa5897e80a25f55b3c45cf2764c9b3ff0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25a0a465dc5ce5a96d2b93d312bab2edeccffdc21781df74a0dd6fae11b1d5f6 0.600000000000 1643763 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": 1158144, "vin": [ { "gen": { "height": 1158134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25a0a465dc5ce5a96d2b93d312bab2edeccffdc21781df74a0dd6fae11b1d5f6" } } ], "extra": [ 1, 194, 37, 183, 2, 184, 0, 129, 53, 233, 3, 82, 51, 147, 214, 87, 208, 170, 88, 151, 232, 10, 37, 245, 91, 60, 69, 207, 39, 100, 201, 179, 255, 2, 17, 0, 0, 0, 4, 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