Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7e63f8e4a994fb58f23c7601fd754d4725c51e3cb2e5dd525ce02cd2788a305

Tx prefix hash: 594d69d30d0c95ab1bcdaf2ac2145fdd3d2cdbe6d84fe63fceda0334f94f8f84
Tx public key: af2fe364154c64488e0c3264f365bace9e2408eb81a352b89a7f42a89092ce34
Timestamp: 1705083755 Timestamp [UCT]: 2024-01-12 18:22:35 Age [y:d:h:m:s]: 01:150:04:08:59
Block: 933876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368480 RingCT/type: yes/0
Extra: 01af2fe364154c64488e0c3264f365bace9e2408eb81a352b89a7f42a89092ce3402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f54c295bf6758da2ddd7676f749c7f014d0536a00fca00d429073e8a1560b031 0.600000000000 1391860 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": 933886, "vin": [ { "gen": { "height": 933876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f54c295bf6758da2ddd7676f749c7f014d0536a00fca00d429073e8a1560b031" } } ], "extra": [ 1, 175, 47, 227, 100, 21, 76, 100, 72, 142, 12, 50, 100, 243, 101, 186, 206, 158, 36, 8, 235, 129, 163, 82, 184, 154, 127, 66, 168, 144, 146, 206, 52, 2, 17, 0, 0, 0, 2, 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