Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 505145cf80995618753a96845b01d7b5969d403609fbb4e64c488d2e14ee135d

Tx prefix hash: f1bf41cef9b422ae4313c57c36db8409c695f2e3a0c995380d59ed1cc285352d
Tx public key: 20afa6c794b9f73801552d4ce44c3c01898c4ed06b6ddf9448f2e0ca69f5aa44
Timestamp: 1722390211 Timestamp [UCT]: 2024-07-31 01:43:31 Age [y:d:h:m:s]: 01:105:15:58:24
Block: 1077369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334010 RingCT/type: yes/0
Extra: 0120afa6c794b9f73801552d4ce44c3c01898c4ed06b6ddf9448f2e0ca69f5aa4402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 288c63330b9bb773c3bfe0b4ec482066bebd6d2832d562fe8b4a7d330b1d57e5 0.600000000000 1549916 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": 1077379, "vin": [ { "gen": { "height": 1077369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "288c63330b9bb773c3bfe0b4ec482066bebd6d2832d562fe8b4a7d330b1d57e5" } } ], "extra": [ 1, 32, 175, 166, 199, 148, 185, 247, 56, 1, 85, 45, 76, 228, 76, 60, 1, 137, 140, 78, 208, 107, 109, 223, 148, 72, 242, 224, 202, 105, 245, 170, 68, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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