Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 430426363faf4dea7844886b627b5031d144539c62e20747514ee21cbd47f4be

Tx prefix hash: 317b1a88d1447362229c6c5518fe9d1a2538eabe0f804f12167e83e174a9ef30
Tx public key: a2f6fd57efe5eaa81771e2daa971e8657d26ee00eb5c27a019d9fd1fe8a23555
Timestamp: 1716894837 Timestamp [UCT]: 2024-05-28 11:13:57 Age [y:d:h:m:s]: 01:018:01:14:51
Block: 1031824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273704 RingCT/type: yes/0
Extra: 01a2f6fd57efe5eaa81771e2daa971e8657d26ee00eb5c27a019d9fd1fe8a235550211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d78574225c725a7060c89275f3b1eb62cdba79750ddb75e7d1e21a85e14678f 0.600000000000 1500273 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": 1031834, "vin": [ { "gen": { "height": 1031824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d78574225c725a7060c89275f3b1eb62cdba79750ddb75e7d1e21a85e14678f" } } ], "extra": [ 1, 162, 246, 253, 87, 239, 229, 234, 168, 23, 113, 226, 218, 169, 113, 232, 101, 125, 38, 238, 0, 235, 92, 39, 160, 25, 217, 253, 31, 232, 162, 53, 85, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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