Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b50e7c3339fc4213cb5af3e7c101747f6223d5a4f7e946899d876e9129e8aee2

Tx prefix hash: f040e665ce77666163fc8c7628f4cf0195390d79e4a5872e81b9cbd1efae1dc9
Tx public key: a3e1775293dca0067ee77285b350a3feb5fa4765c439cce7ce1bd4ce8e8c96f0
Timestamp: 1706343847 Timestamp [UCT]: 2024-01-27 08:24:07 Age [y:d:h:m:s]: 01:310:07:49:59
Block: 944316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480633 RingCT/type: yes/0
Extra: 01a3e1775293dca0067ee77285b350a3feb5fa4765c439cce7ce1bd4ce8e8c96f002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c627ad04d2e27f899b53195fc6baabfa0af010b2c2c50f2e4aa44ba1ae5f1eea 0.600000000000 1402552 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": 944326, "vin": [ { "gen": { "height": 944316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c627ad04d2e27f899b53195fc6baabfa0af010b2c2c50f2e4aa44ba1ae5f1eea" } } ], "extra": [ 1, 163, 225, 119, 82, 147, 220, 160, 6, 126, 231, 114, 133, 179, 80, 163, 254, 181, 250, 71, 101, 196, 57, 204, 231, 206, 27, 212, 206, 142, 140, 150, 240, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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