Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b99a9c605d1bed0d7bee0efc8ca6865440c65e224656ac3c319f49ef6b0fbeec

Tx prefix hash: c440d7cceaa2a4d14c6535620b1472a19693e413b611aceb860fa346ccf9b212
Tx public key: 3ecb098cbc5babfd2bff183a7ee9d001323de42422b4f554f1484aac032404e8
Timestamp: 1731812996 Timestamp [UCT]: 2024-11-17 03:09:56 Age [y:d:h:m:s]: 00:007:04:24:10
Block: 1155384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5156 RingCT/type: yes/0
Extra: 013ecb098cbc5babfd2bff183a7ee9d001323de42422b4f554f1484aac032404e80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d83ce2243a6c1829a210a2156aff2d98b0874935be6f7cc1eb421b600a116fb 0.600000000000 1640999 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": 1155394, "vin": [ { "gen": { "height": 1155384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d83ce2243a6c1829a210a2156aff2d98b0874935be6f7cc1eb421b600a116fb" } } ], "extra": [ 1, 62, 203, 9, 140, 188, 91, 171, 253, 43, 255, 24, 58, 126, 233, 208, 1, 50, 61, 228, 36, 34, 180, 245, 84, 241, 72, 74, 172, 3, 36, 4, 232, 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