Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d17f42166f77158d3cf7a031bbb4b922350ff2fcab1c8b26c8441a853f7af536

Tx prefix hash: 97b016b42c40ef736abb20e5517d13d830f6f1787a58ee94a7fee91507a638d3
Tx public key: 50254e03cb226c5ee45590519593444b2de1785cc2788c74e5fe55a7f6931c75
Timestamp: 1698099450 Timestamp [UCT]: 2023-10-23 22:17:30 Age [y:d:h:m:s]: 01:202:10:49:27
Block: 876194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405733 RingCT/type: yes/0
Extra: 0150254e03cb226c5ee45590519593444b2de1785cc2788c74e5fe55a7f6931c75021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.767018026000 dcy

stealth address amount amount idx
00: 161545ddd3dd1e5dc79bb1111fdfc1d3ea1442b0c22d588c5c149d06738dcd17 0.767018026000 1331504 of 0

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": 876204, "vin": [ { "gen": { "height": 876194 } } ], "vout": [ { "amount": 767018026, "target": { "key": "161545ddd3dd1e5dc79bb1111fdfc1d3ea1442b0c22d588c5c149d06738dcd17" } } ], "extra": [ 1, 80, 37, 78, 3, 203, 34, 108, 94, 228, 85, 144, 81, 149, 147, 68, 75, 45, 225, 120, 92, 194, 120, 140, 116, 229, 254, 85, 167, 246, 147, 28, 117, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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