Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b4401757031b72a5e14ecca3c97c77b0a10919531a11f06262156ad4c7eb91e

Tx prefix hash: 014571be90e6f11ee0ec1d5b9cb6af181a79fdd2d7fcccebf7b24180bd1fc036
Tx public key: 0f3e580379f40ea30f0390fc0bcace2e65f6837bfb8b4296c35885722d66ee6a
Timestamp: 1731286486 Timestamp [UCT]: 2024-11-11 00:54:46 Age [y:d:h:m:s]: 00:012:21:31:44
Block: 1151041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9224 RingCT/type: yes/0
Extra: 010f3e580379f40ea30f0390fc0bcace2e65f6837bfb8b4296c35885722d66ee6a02110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05a350acd16c150b3fba7f872253dd6f3d4f2e63d11c994b4a290164be345b50 0.600000000000 1636496 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": 1151051, "vin": [ { "gen": { "height": 1151041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05a350acd16c150b3fba7f872253dd6f3d4f2e63d11c994b4a290164be345b50" } } ], "extra": [ 1, 15, 62, 88, 3, 121, 244, 14, 163, 15, 3, 144, 252, 11, 202, 206, 46, 101, 246, 131, 123, 251, 139, 66, 150, 195, 88, 133, 114, 45, 102, 238, 106, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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