Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f537b83a2e63a2a2705e2ba6bcca57a6331cceaa97bff71d47ccd5d0199c1409

Tx prefix hash: 0a5e30f6843ac822291d5cd710ed432e8af1f95b873768e9d4e28a1fe783a979
Tx public key: 8fb70509b55ec3119eab679a9c231045819f8ff3b0184804a422b207089b4699
Timestamp: 1709097251 Timestamp [UCT]: 2024-02-28 05:14:11 Age [y:d:h:m:s]: 01:259:06:16:35
Block: 967174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444031 RingCT/type: yes/0
Extra: 018fb70509b55ec3119eab679a9c231045819f8ff3b0184804a422b207089b46990211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ab1b88c78ed833a51abf8aabb24882aa37f47595f7ba164c775c1fbdcbebc8a 0.600000000000 1426945 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": 967184, "vin": [ { "gen": { "height": 967174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ab1b88c78ed833a51abf8aabb24882aa37f47595f7ba164c775c1fbdcbebc8a" } } ], "extra": [ 1, 143, 183, 5, 9, 181, 94, 195, 17, 158, 171, 103, 154, 156, 35, 16, 69, 129, 159, 143, 243, 176, 24, 72, 4, 164, 34, 178, 7, 8, 155, 70, 153, 2, 17, 0, 0, 0, 5, 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