Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43a6dae0b8553d2a377a0941a48255560929bc9a8b69d8f5c5bb45de13232a97

Tx prefix hash: bebb04f85230389e802c0a5b545d1cab85793e440a3d6989a710cbadf707e94a
Tx public key: 82f1e509dcf5b8dd1408d0a22504c471bf51805d3c056717e9462ae89223f294
Timestamp: 1707012801 Timestamp [UCT]: 2024-02-04 02:13:21 Age [y:d:h:m:s]: 01:065:00:09:50
Block: 949872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307521 RingCT/type: yes/0
Extra: 0182f1e509dcf5b8dd1408d0a22504c471bf51805d3c056717e9462ae89223f29402110000000381d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13b499b89f1dd32d6c1e46ff2ac4e9814f101a571251e6da8c3a1972e14bb963 0.600000000000 1408406 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": 949882, "vin": [ { "gen": { "height": 949872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13b499b89f1dd32d6c1e46ff2ac4e9814f101a571251e6da8c3a1972e14bb963" } } ], "extra": [ 1, 130, 241, 229, 9, 220, 245, 184, 221, 20, 8, 208, 162, 37, 4, 196, 113, 191, 81, 128, 93, 60, 5, 103, 23, 233, 70, 42, 232, 146, 35, 242, 148, 2, 17, 0, 0, 0, 3, 129, 215, 29, 85, 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