Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3a4af19bf9678db4cbf29b84ecd94b9d02e33733fd796ddc689e55578a23bbd

Tx prefix hash: e12b6e3046b085acf726d6278fa1b62941d7b6545930469d453f6f3ef7eb7e79
Tx public key: e4bf99209abb81536e67f3be869fe4dbba65a34e81e5a5aacd5a50ef1b59aad7
Timestamp: 1713677694 Timestamp [UCT]: 2024-04-21 05:34:54 Age [y:d:h:m:s]: 00:251:11:22:37
Block: 1005135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180004 RingCT/type: yes/0
Extra: 01e4bf99209abb81536e67f3be869fe4dbba65a34e81e5a5aacd5a50ef1b59aad70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a01b30974307d4f2e12b00a237cde7a9722f96715baef1f3dac2250f080c3d20 0.600000000000 1465715 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": 1005145, "vin": [ { "gen": { "height": 1005135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a01b30974307d4f2e12b00a237cde7a9722f96715baef1f3dac2250f080c3d20" } } ], "extra": [ 1, 228, 191, 153, 32, 154, 187, 129, 83, 110, 103, 243, 190, 134, 159, 228, 219, 186, 101, 163, 78, 129, 229, 165, 170, 205, 90, 80, 239, 27, 89, 170, 215, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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