Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2e6a7bf970e397b9d2d01a1e5cb54db0c2e4d25b22ca6d2565499f34eb146f0

Tx prefix hash: 339fc5e5aadad635810fd17fe6a2aedf04652521dd0421830e9a1cf3f4b73937
Tx public key: c74624925983eacf37dc375cfac0b82fc342033d5ecae5a6eeb32fd8624bfdb6
Timestamp: 1730017104 Timestamp [UCT]: 2024-10-27 08:18:24 Age [y:d:h:m:s]: 00:072:14:16:06
Block: 1140569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51893 RingCT/type: yes/0
Extra: 01c74624925983eacf37dc375cfac0b82fc342033d5ecae5a6eeb32fd8624bfdb6021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f67e6bcd5ff3d9ee31a3cf09c01c1519f21022176ce7fc7913c9c0d8325e0f73 0.600000000000 1624370 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": 1140579, "vin": [ { "gen": { "height": 1140569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f67e6bcd5ff3d9ee31a3cf09c01c1519f21022176ce7fc7913c9c0d8325e0f73" } } ], "extra": [ 1, 199, 70, 36, 146, 89, 131, 234, 207, 55, 220, 55, 92, 250, 192, 184, 47, 195, 66, 3, 61, 94, 202, 229, 166, 238, 179, 47, 216, 98, 75, 253, 182, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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