Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2220e05f6e9bd8c1c0fffa9f1f63c48ed5a4cf89b2d442ebae1d9532dc933ce9

Tx prefix hash: f08f177e45e410b5c2a23bb577eaa0eef4bff7200b866f9e7d4a825f6ddfe06a
Tx public key: d79a61e5bc3fb5c7b38d54714add5a3b805308dd185b0fe5251a89e4751bb39b
Timestamp: 1705717408 Timestamp [UCT]: 2024-01-20 02:23:28 Age [y:d:h:m:s]: 01:079:09:06:48
Block: 939112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317839 RingCT/type: yes/0
Extra: 01d79a61e5bc3fb5c7b38d54714add5a3b805308dd185b0fe5251a89e4751bb39b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10f45c1c00202e12ee6dedd4c1e2fb6de8e7cd08b4b3100f31d2447610510111 0.600000000000 1397196 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": 939122, "vin": [ { "gen": { "height": 939112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10f45c1c00202e12ee6dedd4c1e2fb6de8e7cd08b4b3100f31d2447610510111" } } ], "extra": [ 1, 215, 154, 97, 229, 188, 63, 181, 199, 179, 141, 84, 113, 74, 221, 90, 59, 128, 83, 8, 221, 24, 91, 15, 229, 37, 26, 137, 228, 117, 27, 179, 155, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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