Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 713638d857cde36cfd140259e3e555cdf4ef4c37ed4066e0dbd849d849b3fbb9

Tx prefix hash: 9c24917def597435cd95f57c91ddad8f5705f3a19aa44b8df0482ad95e327658
Tx public key: 8b38a72c213e77b20e259e60e882c02ed78fb648763375cc3acb168c12cbb63d
Timestamp: 1723952684 Timestamp [UCT]: 2024-08-18 03:44:44 Age [y:d:h:m:s]: 00:229:13:35:11
Block: 1090327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163938 RingCT/type: yes/0
Extra: 018b38a72c213e77b20e259e60e882c02ed78fb648763375cc3acb168c12cbb63d02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00caf1e9dba9484f3a22b5a7005aefc17fd6b2b6e8dd74c0b30ddfc380de59b5 0.600000000000 1564950 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": 1090337, "vin": [ { "gen": { "height": 1090327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00caf1e9dba9484f3a22b5a7005aefc17fd6b2b6e8dd74c0b30ddfc380de59b5" } } ], "extra": [ 1, 139, 56, 167, 44, 33, 62, 119, 178, 14, 37, 158, 96, 232, 130, 192, 46, 215, 143, 182, 72, 118, 51, 117, 204, 58, 203, 22, 140, 18, 203, 182, 61, 2, 17, 0, 0, 0, 6, 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