Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b22e9cc8075cd322f5423e1068d83820a3c1a1398b3e4ba320443c871a8c3c4b

Tx prefix hash: 033f5730356f0817ff213a3208616a5c748245bc1484ea3b5564350fce053c8d
Tx public key: 462151b268830827ec758c0c072ef57a4099eeccf091ea46a2041260c5506bc7
Timestamp: 1732107704 Timestamp [UCT]: 2024-11-20 13:01:44 Age [y:d:h:m:s]: 00:134:21:22:20
Block: 1157827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96239 RingCT/type: yes/0
Extra: 01462151b268830827ec758c0c072ef57a4099eeccf091ea46a2041260c5506bc70211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1c7e5eecfcd8fba7c4f6cb9f754305ec9fdfb5f9c869de323f56e21a87c5429 0.600000000000 1643450 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": 1157837, "vin": [ { "gen": { "height": 1157827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1c7e5eecfcd8fba7c4f6cb9f754305ec9fdfb5f9c869de323f56e21a87c5429" } } ], "extra": [ 1, 70, 33, 81, 178, 104, 131, 8, 39, 236, 117, 140, 12, 7, 46, 245, 122, 64, 153, 238, 204, 240, 145, 234, 70, 162, 4, 18, 96, 197, 80, 107, 199, 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